From: Colin Walters <walters@verbum.org>
Date: Tue, 20 Jun 2017 21:19:01 +0000 (-0400)
Subject: ci: Enable -Werror=maybe-uninitialized
X-Git-Tag: archive/raspbian/2022.1-3+rpi1~1^2~4^2~35^2~75
X-Git-Url: https://dgit.raspbian.org/%22http:/www.example.com/cgi/%22https:/%22bookmarks:///%22http:/www.example.com/cgi/%22https:/%22bookmarks:/?a=commitdiff_plain;h=027c77c621bf8557fa1fa45ac77b247a52376131;p=ostree.git

ci: Enable -Werror=maybe-uninitialized

We don't want to inject this warning by default for every build
like the other ones in `configure.ac`, since it can be spruriously
wrong.  But there's no reason not to have a more extended set of
warnings for well-known toolchains (e.g. f25).

Closes: #943
Approved by: jlebon
---

diff --git a/.papr.yml b/.papr.yml
index 6946b936..1addf061 100644
--- a/.papr.yml
+++ b/.papr.yml
@@ -12,7 +12,9 @@ packages:
   - git
 
 env:
-    CFLAGS: '-fsanitize=undefined -fsanitize-undefined-trap-on-error -fsanitize=address -O2 -Wp,-D_FORTIFY_SOURCE=2'
+    # Enable all the sanitizers for this primary build.
+    # We only use -Werror=maybe-uninitialized here with a "fixed" toolchain
+    CFLAGS: '-fsanitize=undefined -fsanitize-undefined-trap-on-error -fsanitize=address -O2 -Wp,-D_FORTIFY_SOURCE=2 -Werror=maybe-uninitialized'
     ASAN_OPTIONS: 'detect_leaks=0'  # Right now we're not fully clean, but this gets us use-after-free etc
     # TODO when we're doing leak checks: G_SLICE: "always-malloc"